IBM(R) Networks Primary Logon Client 4.5 for Windows NT(R) 4.0, 
Windows 2000 Professional, and Windows XP Professional

This README contains information on installing and using 
the IBM Networks Primary Logon Client 4.5 for Windows NT 4.0, 
Windows 2000 Professional, and Windows XP Professional, 
also called "IBM Networks Client."

NOTE: Pay particular attention to Section 3.0 Installing IBM Networks Client.

If there are any updates to this README, the updates will be placed on 
the "Software Group Support News Items" Web site. This Web site contains 
a list of fix-related news items. The Web address is:

 http://ps.software.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa/fixnews.html/#plc

________
CONTENTS
________

1.0  Introduction
2.0  Prerequisites
3.0  Installing IBM Networks Client
     3.1  Installation
     3.2  Installation configuration file
     3.3  Installing from IBM OS/2 Warp Server
4.0  Using IBM Networks Client
     4.1  Logging on
     4.2  Starting the IBM Networks Client GUI
     4.3  Displaying the User's Guide
     4.4  Changing the IBM Networks Client configuration
     4.5  Using group mapping
     4.6  Using the RoamingUsers group
5.0  DCE Information
     5.1  DCE cell name format
     5.2  DFS home directory drive letter
     5.3  System policy file storage format
     5.4  DCE credentials
6.0  Troubleshooting
     6.1  Password synchronization error message
     6.2  "A slow link has been detected. . ." error message
     6.3  New profile directory for each logon
     6.4  Installing a Windows NT Service Pack
     6.5  Logon Error -- "Domain not available" message
     6.6  "Failed Logon" behavior considerations
7.0  Removing IBM Networks Client
     7.1  Removing IBM Networks Client from the Control Panel
     7.2  Removing the IBM Networks Client using the uninstall option
8.0  Windows 2000 and Windows XP Professional Considerations
9.0  Discover Option and Manual Domain Entry Considerations
     for Windows XP Professional
10.0 Windows 2000 and Windows XP NETBIOS Name Support
     10.1 Using a NETBIOS Name Server
     10.2 Using the LMHOSTS File 
     10.3 Using Both WINS and LMHOSTS on the Client
11.0 Profile.bat Considerations
12.0 Trademarks


1.0 INTRODUCTION
________________

The IBM Networks Primary Logon Client 4.5 for Windows NT 4.0, Windows 2000 
Professional, and Windows XP Professional is an add-on to the Microsoft(R) 
Windows Network function.
With the IBM Networks Client, you can access the resources provided by
an IBM OS/2(R) Warp Server domain, including the following:

o  Connecting to home directories
o  Setting up and connecting to logon assignments
o  Running shared applications
o  Connecting to aliases
o  Checking DASD limits

A user's home directory and logon assignments are automatically connected
after the user successfully logs on to and is authenticated on an OS/2 Warp
Server domain or DCE cell.

2.0  PREREQUISITES
__________________

For OS/2 Warp Server for e-business, type NET START BROWSER at 
a command prompt and add it to the list of services in the IBMLAN.INI
that autostart at startup.

The following components are prerequisites for the IBM Networks
Client:

o  Microsoft Windows NT Version 4.0 plus service pack 6a and the Microsoft
   Active Directory Client Extension, Windows 2000 Professional, or
   Windows XP Professional workstation
o  NetBEUI or TCP/IP

The following additional component is a prerequisite for 
Distributed Computing Environment (DCE) authentication from
the IBM Networks Client:

o  IBM Distributed Computing Environment 2.0
   for Windows NT or Gradient PC-DCE v2.0 for Windows NT


3.0  INSTALLING IBM NETWORKS CLIENT
___________________________________

IBM Networks Client is installed using an installation configuration file
to provide client configuration information. The following sections
describe the installation, the installation configuration file, and how
to install the IBM Networks Client from an IBM OS/2 Warp Server.

Note:  If you installed a previous version of the IBM Networks Client,
       you must remove those files before installing this version. To 
       remove the files, follow the instructions in section 7.0, 
       "Removing IBM Networks Client."

3.1  Installation
------------------
Use the following instructions to install the IBM Networks Client on
a Windows NT, Windows 2000, or Windows XP Professional system.

NOTE: After installation, your system will automatically restart. If
      you do not want your system to automatically restart, complete
      the following steps before installation to disable automatic
      restart:

          1.  Open the SETUP.ISS file (located in the c:\<client>\install
              directory, where c:\<client> is the drive and directory
              where you downloaded and unzipped the IBM Networks Client
              Package) in a flat editor.

          2.  In the [SdFinishReboot-0] section, change the
              BootOption key from 3 to 0.

          3.  Save the file.

Installation instructions:
--------------------------
1.  Log on to the system with a user name that has administrator privileges.

2.  At a command prompt, change to the directory where you downloaded
    and unzipped the IBM Networks Client package and type the following
    command, specifying the -d option, to finish unzipping the
    IBM Networks Client package:

         plc45 -d

3.  Open the IBMNETNT.INI file in a flat editor. This file, the
    installation configuration file, is in the directory where you
    downloaded and unzipped the IBM Networks Client package.

4.  Type the name of your default logon domain on the DefaultCellDomain=
    line.

    For example, if the name of the domain is "logon1," the line would
    be "DefaultCellDomain=logon1". For more information about the
    installation configuration file and the parameter definitions,
    see Section 3.2, "Installation configuration file."

5.  Save the changed file and exit.

6.  At a command prompt, change to the directory where you downloaded
    and unzipped the IBM Networks Client package and type the following
    command to launch the installation:

         path\setup ini=ConfigurationFile log=ResultsFile silent

    where the variables and parameters have the following meanings:

    path\setup               Required. The fully qualified path to
                             the SETUP.EXE file for installation.

    ini=ConfigurationFile    Optional. The fully qualified path to
                             the installation configuration file.
                             For more information about the
                             installation configuration file, see
                             section 3.2, "Installation configuration
                             file."

                             NOTE: If a file name is specified without
                             a path, the directory where the SETUP.EXE
                             file is located is used by default. If no
                             file is specified, the IBMNETNT.INI file
                             is used. If neither a specified nor a
                             default configuration file is found, the
                             installation will fail.

    log=ResultsFile          Optional. The fully qualified path to an
                             output result file. The ResultsFile is
                             created only if you specify the silent
                             parameter.

                             NOTE:
                             o  If a path is not specified, the file
                                is created in the directory where the
                                installation configuration file is
                                located. If a file name is not 
                                specified, the name of the installation
                                configuration file, with the extension 
                                .LOG, is used.


    silent                   Optional. Specifies unattended installation
                             mode. Messages are written to the log file,
                             instead of being displayed as pop-up messages.

    NOTE:  You can use the above parameters with either colons or
           equal signs.  For example, "log:" is equivalent to "log=".
           However, there cannot be a space before or after the
           colon or equal sign.

7.  After installation is complete, your system will shut down and
    restart automatically unless you disabled automatic restart per the
    note in Section 3.1.

3.2  Installation configuration file
-------------------------------------
The installation configuration file is an editable file, consistent
with the Windows initialization file format, that provides client
configuration information that is needed during the installation
process.  The file contains the following sections and parameters:

  [PrimaryAuthentication]
  DefaultCellDomain=domainname
  OtherCellDomains=othercell1,othercell2,othercell3
  EnableDomainDiscovery=n
  EnableDomainEntry=n
  EnableStartMenu=n

  [SecondaryAuthentication]
  EnableAuthentication=n
  WarpServerDomain=wdomainname
  SpecifyLogonServer=n
  LogonServer=servername
  LogonBroadcastAttempts=n
  LogonBroadcastWait=n

  [ProfileBatWindow]
  DisplayProfileBatWindow=0

NOTE:  You must have a blank line at the end of this file.

These parameters have the following definitions:

[PrimaryAuthentication]      Required section name.

DefaultCellDomain            Required. Specifies the default logon
                             domain.


OtherCellDomains             Optional. Specifies other domains to
                             list on the logon window.

                             NOTE: Multiple domains can be listed
                             on the same line, separated by commas
                             or as separate entries.  For example,
                             "otherCellDomains=cell1,cell2,cell3"
                             is equivalent to the following:
                                  "OtherCellDomains=cell1
                                   OtherCellDomains=cell2
                                   OtherCellDomains=cell3"

EnableDomainDiscovery        Optional. A numeric parameter that
                             enables domain searching on the logon
                             window.  The valid values are as
                             follows:
                                  1     Enable domain discovery from
                                        the logon window. (default)
                                  0     Do not allow domain discovery.

EnableDomainEntry            Optional. A numeric parameter that
                             specifies whether or not a domain name
                             can be manually entered at the logon
                             window. The valid values are as follows:
                                  1     Enable domain entry at the
                                        logon window. (default)
                                  0     Do not allow domain entry.

EnableStartMenu              Optional. A numeric parameter that
                             specifies whether or not to install
                             the "User's Guide" and graphical user
                             interface (GUI) on the Start Menu.
                             The valid values are as follows:
                                  1     Install the "User's Guide"
                                        and GUI. (default)
                                  0     Do not install the "User's
                                        Guide" and GUI.

[SecondaryAuthentication]    Optional section name.

EnableAuthentication         Optional. A numeric parameter that
                             specifies whether or not to enable
                             secondary authentication.  The valid
                             values are as follows:
                                  0     Do not enable secondary
                                        authentication. (default)
                                  1     Enable secondary authentication.

WarpServerDomain             Required when EnableAuthentication=1.
                             Specifies the name of the OS/2 Warp
                             Server domain to provide secondary
                             authentication.

SpecifyLogonServer           Optional. A numeric parameter that
                             indicates if the logon server for
                             secondary authentication is specified.
                             The valid values are as follows:
                                  0     Do not specify the logon
                                        server. (default)
                                  1     Specify the logon server.

LogonServer                  Required when SpecifyLogonServer=1.
                             The name of the preferred logon server
                             for authentication at logon.

LogonBroadcastAttempts       Optional. A numeric parameter that specifies
                             the number of broadcast attempts at
                             logon.  The default value is 4, and
                             valid values range from 1 to 1024.

LogonBroadcastWait           Optional. A numeric parameter that specifies,
                             in seconds, the wait period for a response
                             to a broadcast message. The default value is
                             18, and valid values range from 1 to 1024.

[ProfileBatWindow]           Optional section name. 

DisplayProfileBatWindow      Optional.  A numeric parameter that specifies
                             whether the window used to run profile.bat
                             will be hidden or visible.
                             The valid values are as follows:
                                  0     The window is hidden and not
                                        accessable by the user. (default)
                                  1     The window is visible and accessable
                                        by the user.  Specify this value
                                        when user interaction with the
                                        profile.bat file is desired.

3.3  Installing from IBM OS/2 Warp Server
-----------------------------------------
To install the IBM Networks Client from an IBM OS/2 Warp
Server:

1.  On the IBM OS/2 Warp Server system, create a network share that
    contains the IBM Networks Client installation files:

    a.  Create a directory named x:\IBMWINNT, where x: is the
        drive letter.

    b.  Download and run the IBM Networks Client package in the
        x:\IBMWINNT directory.

    c.  Create a shared resource by typing the following command
        in an OS/2 Window:

        NET SHARE IBMWINNT=x:\IBMWINNT

    d.  Set the access controls for this share by typing the
        following command:

        NET ACCESS x:\IBMWINNT /ADD GUESTS:RX USERS:RX

2.  On the Windows system, map a drive to the IBMWINNT network
    share:

    a.  In the Windows Explorer, click Tools --> Map Network
        Drive.

    b.  In the Drive field of the Map Network Drive window, select
        a drive letter.

    c.  In the Shared Directories list, find the IBM OS/2 Warp
        Server name and double-click the IBMWINNT share.

    d.  Click OK.

3.  At a command prompt, change to the IBMWINNT drive.

4.  Continue with the installation instructions in section 3.1.


4.0  USING IBM NETWORKS CLIENT
______________________________

The following sections describe how to use the IBM Networks Client.

4.1  Logging on
----------------
To log on to the IBM Networks Client:

1.  Type your user name in the User Name field and your password
    in the Password field.

2.  In the Domain field, type the name of the domain you want to
    log on to or select the domain from the drop-down list.

    NOTE: If the list is empty or the domain that you want to use
          to log on is not listed, click Discover. The network is
          searched for available domains and the list is updated
          with all the Windows NT, Windows 2000, and OS/2 Warp 
          Server domains that the network finds.

3.  Click OK to start the authentication of your IBM Networks
    Client user name and password.

4.2  Starting the IBM Networks Client GUI
------------------------------------------
To start the IBM Networks Client GUI:

1.  Click Start --> Programs --> IBM Networks Client (Common).

2.  Click IBM Networks Client.

    When running on a client that uses only the NETBIOS over TCP/IP
    protocol, the GUI may take 20-30 seconds to display.  In addition,
    network resource requests initiated by selecting GUI options may
    take 20-30 seconds to complete.

Note: You can use the Windows Network Neighborhood to view and
      connect network resources.

4.3  Displaying the User's Guide
--------------------------------
The "IBM Primary Logon Client User's Guide" contains information
about using the IBM Networks Client.

To display the "IBM Primary Logon Client User's Guide":

1.  Click Start --> Programs --> IBM Networks Client (Common).

2.  Click User's Guide.

4.4  Changing the IBM Networks Client configuration
----------------------------------------------------
To change the configuration of the IBM Networks Client
configuration after installation:

1.  Log on to the system with a user name that has administrator privileges.

2.  Click Start --> Settings --> Control Panel.

3.  Double-click Network.

4.  Click the Services tab of the Network notebook.

4.  Click IBM Networks Primary Logon Client and then click Properties to
    display the IBM Networks Primary Logon Client configuration notebook.

NOTE: You can enable secondary authentication through the configuration
      notebook. To enable secondary authentication:

      1.  Click the SMB tab on the IBM Networks Primary Logon Client
          properties notebook.

      2.  Select Allow Secondary Authentication.

      3.  Specify the name of the OS/2 Warp Server domain where secondary
          authentication will occur and click OK.

      4.  Click OK.

      To use secondary authentication on an OS/2 Warp Server domain, your
      Windows and OS/2 Warp Server user accounts must be synchronized.

4.5  Using group mapping
-------------------------
Group mapping allows you to add members of a domain group to a
specified local group during logon.

For example, to give administrators from domain WSDOM administrative
rights to your local Windows NT workstation, you can add users that
are members of the "ADMINS" group in WSDOM to the "Administrators"
group on the local Windows NT workstation.

To add a group mapping:

1.  Add the "GroupMapping" key to the workstation's registry, if it
    is not already present.

    a. Start REGEDT32.
    b. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMNeTNT.
    g. Click Edit --> Add Key.
    h. Type "GroupMapping" in the key name field.

2.  Click the "GroupMapping" key.

3.  Click Edit --> Add Value.

4.  Type the name of the domain group. The data type for the name
    should be REG_SZ.

    For example, WSDOM_ADMINS is the name of the "ADMINS" group
    in the "WSDOM" domain.

5.  Click OK.

6.  In the String Editor dialog box, type the name of the local group
    that you want members of the domain group to be added to.

    For example, typing "Administrators" would add members of the
    "WSDOM_ADMINS" group to a group with local administrator rights.

7.  Click OK and close REGEDT32.

At the next logon, members of the ADMINS from the WSDOM domain will
have administrative rights on your workstation.  You do not have
to restart the system for changes to the GroupMapping key to take
effect.

4.6 Using the RoamingUsers group
---------------------------------
The RoamingUsers group allows the IBM Networks Client to control
how user accounts are handled during logon.

Accounts in the RoamingUsers group are affected  at logon in the
following ways:

o  They are removed from any groups they are a member of prior
   to logon (except for the RoamingUsers group).
o  They are added to their domain or cell groups.
o  Their passwords might be automatically synchronized with their
   network password (if the passwords are unsynchronized).

NOTES:
      o  Accounts created dynamically by IBM Networks Client are
         automatically added to the RoamingUser group.
      o  Accounts that are not in the RoamingUsers group are not
         affected at logon.
      o  User accounts are not automatically migrated to the
         RoamingUser group during installation.
      o  If resource access is based on local group membership,
         change access rights to include the domain or cell group
         of which the user is a member.

  Disabling roaming profiles
  ---------------------------
  You can disable roaming profile support in order to reduce network
  bandwidth usage.

  To disable roaming profile support, do the following:

  1.  Start REGEDT32.

  2.  Go to
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMNeTNT\Parameters.

  3.  Click Edit --> Add Value.

  4.  Create a value named "DisableRoamingProfiles" with the REG_DWORD
      data type.

  5.  Click OK.

  6.  In the DWORD Editor dialog box, type "1" in the Value data field.

  7.  Click OK and close REGEDT32.

  The change takes effect on the next logon.


5.0  DCE INFORMATION
_____________________

The following information is for systems using DCE cells.

5.1  DCE cell name format
--------------------------
The cell name must use the following format: /.../cellname

5.2  Distributed File System (DFS) home directory drive letter
-------------------------------------
The mapped drive for a DFS home directory is set to the first
available drive letter by default. You can specify the drive letter
by setting it as a registry value.

To set the DFS home directory drive letter in the registry, use the
following steps:

1.  Add the "HomeDirectory" key to the Windows 2000 or Windows NT
    workstation's registry, if it is not already present.

    a. Start REGEDT32.

    b. Go to
       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMNeTNT\Parameters.

    c. Click Edit --> Add Value.

    d. Create a new value named "HomeDirectoryDrive" with the REG_SZ
       data type.

2.  Click OK.

3.  In the String Editor dialog box, type x:\, where x is the DFS home
    directory drive letter.

4.  Click OK and close REGEDT32.

5.3  System policy file storage format
---------------------------------------
You can store system policy files in DFS as long as they are in
the following format: \\...\cellname\fs\{path}

1.  Add the "DFSPolicyPath" name-value pair to the Windows 2000 or
    Windows NT workstation's registry if it is not already present.

    a. Start REGEDT32.

    b. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMNeTNT\Parameters.

    c. Click Edit --> Add Value.

    d. Create a new value named "DFSPolicyPath" with the REG_SZ data type.

2.  Click OK.

3.  In the String Editor dialog box, type the DFS path of the system
    policy file.

5.  Click OK and close REGEDT32.

5.4  DCE credentials
--------------------
DCE credentials are refreshed when the display is unlocked.


6.0  TROUBLESHOOTING
____________________

The following sections contain information about error messages
and how to work around them.

6.1  Password synchronization error message
--------------------------------------------
The following message might appear during logon:

"The system could not log you on.  Your network account and password
are correct, but your local account password is out of sync.  Contact
your system administrator to synchronize your passwords."

If you see this message, the local account is not marked as a roaming
user (see Section 4.5).  This message appears if the local password
is not the same as the network password, if the local account has
expired or been disabled, or if the local password has expired.

To correct the problem, the local administrator must do one of the
following things:

o  Make the account a roaming user
o  Synchronize the network and local password for the user
o  Re-enable the account

6.2  "A slow link has been detected. . . " error message
--------------------------------------------------------
To avoid the "A slow link has been detected. . ." error message,
disable the slow link detection in the Windows NT registry:

1.  Start REGEDT32.

2.  Go to
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

3.  Add the following value name in the registry and set the value as
    shown below:

                Value Name      :       SlowLinkDetectEnabled
                Data Type       :       REG_DWORD
                Data            :       0

4.  Click OK and close REGEDT32.

6.3  New profile directory for each logon
------------------------------------------
To prevent creating a new user profile directory for each logon,
change the logoff policy from Delete to Keep or Disable.  See
"Managing dynamic local accounts" in the User's Guide for
instructions.

If you need to keep the logoff policy as Delete, then you can
change how Windows NT and Windows 2000 manages cached roaming
profiles. To do this, set the value in the Windows Registry:

1.  Start REGEDT32.

2.  Go to
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

3.  Add the following value name in the registry and set the value as
    shown below:


                Value Name      :       DeleteRoamingCache
                Data Type       :       REG_DWORD
                Data            :       1

4.  Click OK and close REGEDT32.

NOTE: This does not clean up previously cached roaming profiles.
      Previously cached profiles must be deleted manually.

6.4  Installing a Windows NT Service Pack
-----------------------------------------
A system trap might occur after you install a Windows NT Service Pack
on a system with the IBM Networks Client. This trap may occur if the
Service Pack overlays some of the IBM Networks Client files. To prevent
this, before installing the Windows NT Service Pack, use the IBMNETNT.BAT
utility to backup and restore the IBM Networks Client files. Complete the
following steps:

1.  Run IBMNETNT.BAT in the directory where you downloaded and unzipped
    the IBM Networks Client package.

    NOTE: To run the IBMNETNT.BAT utility, you must have the
          IBMNETNT.REG file in the same directory as the IBMNETNT.BAT
          file.

2.  Install the Windows NT Service Pack.

3.  Shut down and restart your system.

As the system restarts, the IBM Network Client files are automatically
restored.

6.5 Logon Error -- "Domain not available" message
-------------------------------------------------

The "Domain not available" error message is displayed for a number of
different situations.  Some of the possible causes are listed below:

1.  On Windows NT clients, Service Pack 6a, the Microsoft
    Active Directory Client Extension, or both might not be installed.  
    Both are required.

    You can determine the Service Pack level by running the Windows
    program WINVER.EXE.  WINVER.EXE displays the current Windows NT
    version information and Service Pack level.

    A utility, IBMCHKDS.EXE, is provided with the IBM Networks Client
    that checks for the presence of the Active Directory Client
    Extension. Run IBMCHKDS.EXE. If the Active Directory Client
    Extension is present, the message "The operation completed
    successfully" is displayed in a message dialog box.

    If the Active Directory Client Extension is not present, the message
    "The specified procedure could not be found" is displayed in
    a message dialog box.  

2.  The Windows client can not resolve the OS/2 NETBIOS domain name
    to an IP address. Refer to section "10.0 Windows 2000 and Windows XP
    Professional NETBIOS Name Support" for information on procedures
    to resolve this problem.

3.  When logging on to an OS/2 domain that is in another IP subnet,
    the client Workgroup name can not be the same as the OS/2 domain
    name.  If necessary, update the client Workgroup name to be different
    from all OS/2 domain names to which the client logs on.


6.6 "Failed Logon" behavior considerations 
------------------------------------------

When a logon fails, the default behavior is to redisplay the logon
panel and wait for another logon attempt.  In some customer environments,
an alternate behavior of returning to the "Press Cntl+Alt+Del to Logon"
panel is desired (see APAR IC32827).  You can configure this alternate 
behavior by creating a special key in the registry. 

To create the special key, do the following:

1. Start REGEDT32.

2. Go to

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMNeTNT\networkprovider

3. Click Edit --> Add Value.

4. Create a new value named "GetReturnVal" with the REG_DWORD data type.

5. Click OK.

6. In The DWORD Editor dialog box, type "1" in the Value data field.

7. Click OK and close REGEDT32.


7.0  REMOVING IBM NETWORKS CLIENT
_________________________________

You can remove the IBM Networks Client using the following methods:

o  At the Control Panel, remove IBM Networks Client from the Network
   folder. This procedure only works on Windows NT 4.0 workstation.
o  Use the uninstall option included with the IBM Networks Client
   package in an attended or unattended mode.

7.1  Removing IBM Networks Client from the Control Panel
--------------------------------------------------------
Use the following instructions to uninstall the IBM Networks Client on
a Windows NT 4.0 system. This procedure will not work on Windows 2000
Professional or Windows XP Professional.

1.  Log on to the system using a user ID with administrator privileges.

2.  Click Start --> Settings --> Control Panel.

3.  Double-click Network.  The Network notebook is displayed.

4.  Click the Services tab.

5.  From the Network Services list, click IBM Networks Primary
    Logon Client.

6.  Click Remove.

7.  Click Yes, and then click Close.

8.  Restart your system.

9.  After your system restarts, log on using a user name with
    administrator privileges to allow the system to complete the
    update of Registry entries and the removal of the IBM Networks
    Client files.

7.2  Removing the IBM Networks Client using the uninstall option
-----------------------------------------------------------------
Use the following instructions to uninstall the IBM Networks Client.
This method will work on Windows NT 4.0, Windows 2000 Professional, 
and Windows XP Professional.

NOTE: After uninstallation, your system will automatically restart. If
      you do not want your system to automatically restart, complete
      the following steps before uninstallation to disable automatic
      restart:

          1.  Open the SETUP.ISS file (located in the c:\<client>\uninstal
              directory, where c:\<client> is the drive and directory
              where you downloaded and unzipped the IBM Networks Client
              Package) in a flat editor.

          2.  In the [SdFinishReboot-0] section, change the
              BootOption key from 3 to 0.

          3.  Save the file.

Uninstallation instructions:
----------------------------
1.  At a command line, change to the directory where you downloaded and
    unzipped the IBM Networks Client Package.

2.  Type the following command:

    path/setup remove log=ResultFile silent

    where path/setup is the fully qualified path of the SETUP.EXE
    file for IBM Networks Client, log=ResultFile is an optional
    output result file, and silent specifies an unattended uninstall.

    NOTES:
          o  If the silent parameter is not specified, errors and
             messages are displayed on the screen. No log file is
             created, even if the log= parameter is specified.

          o  If the silent parameter is specified without the log=
             parameter, a default log file ("IBMNETNT.LOG") is created
             in the directory where you downloaded and unzipped the IBM
             Networks Client Package.

          o  If the remove parameter is not specified, SETUP attempts to
             install, rather than remove, the IBM Networks Client.

3.  After uninstallation is complete, your system will shut down and
    restart automatically unless you disabled automatic restart.

4.  When your system restarts, log on using a user name with
    administrator privileges to allow the system to update the registry
    entries and remove the IBM Networks Client files.

8.0  WINDOWS 2000 and WINDOWS XP PROFESSIONAL CONSIDERATIONS
____________________________________________________________

The Windows 2000 and Windows XP Professional operating systems include
a new feature called Windows File Protection, which helps prevent system
files such as NET.EXE from being overlayed. As a result, to access IBM 
network extensions from an MS-DOS command prompt NETWS.EXE must be run.  
For example, to connect to a Warp Server network shared resource using 
an alias name, use the following command:

  NETWS  X:  ALIAS_NAME

  Where "X:" is an available local drive letter and "ALIAS_NAME" is the
  name of the Warp Server network shared alias.


9.0 DISCOVER OPTION AND MANUAL DOMAIN ENTRY CONSIDERATIONS 
    FOR WINDOWS XP PROFESSIONAL
__________________________________________________________

The Discover option presents a list of domain names that are currently
defined to the network browse master.  OS/2 domain names can be present
in this list and selected for use.  Alternately, an OS/2 domain name
can be manually entered in the domain name field.  However, that does not
mean that the OS/2 domain is available for use.  OS/2 domain names are
actually NETBIOS names and must be resolved to an IP address before the
domain can be contacted.  Methods for handling the NETBIOS name to IP address
resolution are discussed in Section 10.0 "Windows 2000 and Windows XP NETBIOS 
Name Support."

If the NETBIOS name cannot be resolved to an IP address, the
following error message is displayed during logon:

    The system cannot log you on now because the domain 'xxxxxxxx' is
    not available.

where, "xxxxxxxx" is the domain name. 

10.0 WINDOWS 2000 AND WINDOWS XP PROFESSIONAL NETBIOS NAME SUPPORT
__________________________________________________________________

OS/2 servers use NETBIOS names for machine-to-machine identification.
The NETBEUI protocol was used to resolve these names within a subnet.
Starting with Windows 2000, TCP/IP was the default protocol instead of 
NETBEUI.  However, NETBEUI was still available and could be installed
or installed and configured. In Windows XP, NETBEUI support has been 
dropped and is not available as a supported protocol.

The following sections describe how OS/2 NETBIOS name resolution can 
be handled in the Windows 2000 and Windows XP Professional cases where 
NETBEUI is not available or where the OS/2 machines are on a different 
subnet.  There are two ways to provide the required NETBIOS name resolution:

  1. Use a NETBIOS name server (WINS in Windows terminology).
  2. Define NETBIOS names in the LMHOSTS file.


10.1 Using a NETBIOS Name Server
--------------------------------

A NETBIOS Name server must be configured on the network. Some possibilities
for NETBIOS Name servers are:

 o Shadow IPserver which is available from Essential Networks Inc. as a
   hardware product(IPserver) or a software product that runs on Windows NT.

 o A Linux machine running the Samba server distribution. Samba includes a
   NETBIOS name server function.

 o Microsoft Windows WINS which usually runs on a Microsoft Windows 2000 server.


Each OS/2 server should be configured as follows:

 o OS/2 NETBIOS over TCP/IP should be configured on logical adapter 0 with the
   following parameters specified:

   - Node Type: H-Node

   - NETBIOS Name Server Address: x.x.x.x

     where "x.x.x.x" is the IP address of the NETBIOS name server.

   - Backup NETBIOS Name Server Address: x.x.x.x

     where "x.x.x.x" is the  optional IP address of an alternate NETBIOS
     name server.

   - NETBIOS Data Distributor Address: x.x.x.x

     where "x.x.x.x" is the IP address of the NETBIOS Data Distributor,
     usually the same as the NETBIOS Name server.

   - Backup NETBIOS Data Distributor Address: x.x.x.x

     where "x.x.x.x" is the optional IP address of the NETBIOS Data
     Distributor, usually the same as the alternate NETBIOS Name server.

 o The browser service must be started on the OS/2 server.  The browser
   service registers the NETBIOS machine name and domain names with 
   the NETBIOS Name server.

Each Windows client running Primary Logon Client should configure the TCP/IP
protocol to use the WINS server.


10.2 Using the LMHOSTS File
---------------------------

The LMHOSTS file can be used to map NETBIOS names to IP addresses.

The TCP/IP protocol should be configured to use the LMHOSTS file to
resolve names.

On Windows 2000, the LMHOSTS file is located in the following directory:
 
  c:\WINNT\SYSTEM32\DRIVERS\ETC

On Windows XP Professional, the LMHOST file is located in the following
directory:

  c:\WINDOWS\SYSTEM32\DRIVERS\ETC

If a LMHOSTS file does not exist, create it by copying the LMHOSTS.SAM
file to the LMHOSTS file.  Use an editor such as Notepad to update the 
LMHOSTS file to add entries for the appropriate NETBIOS names.  

The following set of entries should be added for each OS/2 Primary
Domain Controller:

   x.x.x.x     SRVNAME1         [#PRE]  #DOM:SRVNAME1DOM
   x.x.x.x     SRVNAME1DOM      [#PRE]
   # template  "123456789012345/0Xnn"
   x.x.x.x     "SRVNAME1DOM    /0X1B"  [#PRE]

The following entry should be added for each additional OS/2 server
that is a member of the SRVNAME1DOM domain:

   x.x.x.x     SRVNAME2         [#PRE]  #DOM:SRVNAME1DOM

where x.x.x.x is the IP address of the OS/2 server. SRVNAME1 and SRVNAME2
are OS/2 server names (from the IBMLAN.INI file). SRVNAME1DOM is the OS/2
server domain name (from the IBMLAN.INI file).

The [#PRE] parameter is optional.  If #PRE is specified, the name is
preloaded at boot time into a memory cache and Windows does not have to
open and read LMHOSTS each time it needs to resolve the name.

The "# template ..." entry, is a comment to provide a template for correctly
entering the special SRVNAME1DOM<1B> entry in the next line.  The special
entry line maps a special NETBIOS name, "SRVNAME1DOM    /0X1B". It is the
domain name padded to 15 characters with blanks plus the hex character
x'1B'. The entire name must be enclosed in double quotes.

All OS/2 NETBIOS names in LMHOSTS must be uppercase.

Using a LMHOSTS file for name resolution of manually entered 
domain names can be problematic. The LMHOSTS file must be preloaded with 
the most commonly used OS/2 domain names.  If a user enters a name that 
is not in the LMHOSTS file, the logon will fail.


10.3 Using Both WINS and LMHOSTS on the Client
----------------------------------------------

Windows 2000 and Windows XP Professional can be configured to use both 
WINS and LMHOSTS. If the Windows DNS service cannot resolve the name 
(NETBIOS names cannot be resolved by DNS), Windows tries to 
resolve the name using WINS. If that fails, Windows tries using the 
LMHOSTS file (if present).


11.0 PROFILE.BAT CONSIDERATIONS
_______________________________

By default, the profile.bat file is run in a hidden window.  This window 
is not accessable to the user.  If commands that require user interaction 
are placed in profile.bat, the hidden window will pause waiting for 
user input.  However, since the window is not visible or accessable to the 
user, the user can not respond. If this occurs, the only action possible 
is to use the Windows Task Manager to terminate the CMD.EXE session that 
is running the profile.bat file.

Version 4.5 of Primary Logon Client has added the ability to configure the
window used to run profile.bat to be visible and user accessable.  There
are two methods to do this:

 o Prior to installing version 4.5, update the default ibmnetnt.ini 
   file and set the DisplayProfileBatWindow parameter to 1.

 o On an installed system, use a registry editor such as regedt32.exe
   to update the following key value:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMNeTNT\networkprovider\ProfileHide

When ProfileHide is 0 (default), the profile.bat runs in a hidden
window. When ProfileHide is 1, the profile.bat runs in a visible 
window with which the user can interact.


12.0 TRADEMARKS
______________

The following terms are trademarks of the International
Business Machines Corporation in the United States,
or other countries, or both:

IBM
OS/2

Microsoft, Windows NT, and the Windows logo are either 
registered trademarks or trademarks of Microsoft Corporation 
in the United States, other countries, or both. 

Other company, product, and service names may be trademarks
or service marks of others.

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER
EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE
AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN
THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS
NO LICENSES TO ANY PATENTS OR COPYRIGHTS.

(C) Copyright IBM Corporation 2002.  All rights reserved.
U.S. Government Users Restricted Rights -- Use, duplication or 
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.